Ofmcc 6357 2 year supp term #392
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
OFMCC-6203 - wording updates
…le type cannot update Licence info
OMFCC-6318 - Bug fix Licence Detail for Provider having Multiple type
…two term app should be displayed
…57-2-year-supp-term main
weskubo-cgi
requested changes
Oct 25, 2024
weskubo-cgi
approved these changes
Oct 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Supplementary applications renewal should work for providers regardless if they have 2 or 3 years on their Funding Agreements.
Improved the banner messaging and hiding the next term button when nearing the end of their Funding agreement.
NOTE: there is a new Vue Warn message regarding props being passed to the SuppSubmit page. I don't know why suddenly it's decided to complain about that?
However - we manually reload the FA through the guid in the URL on the Supp Submit page - so we don't want to use the router-view props. I think we are safe to ignore the warning message but open to suggestions about this